home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
ftp.cs.arizona.edu
/
ftp.cs.arizona.edu.tar
/
ftp.cs.arizona.edu
/
icon
/
newsgrp
/
group94a.txt
/
000000_icon-group-sender _Thu Jan 6 22:46:36 1994.msg
next >
Wrap
Internet Message Format
|
1994-08-19
|
779b
Received: by cheltenham.cs.arizona.edu; Thu, 6 Jan 1994 21:31:46 MST
Date: 6 Jan 94 22:46:36 GMT
From: walter!news@rutgers.edu (Darren New)
Organization: Bellcore
Subject: Re: Icon and sockets
Message-Id: <CJ8CLp.EqF@walter.bellcore.com>
Sender: icon-group-request@cs.arizona.edu
To: icon-group@cs.arizona.edu
Status: R
Errors-To: icon-group-errors@cs.arizona.edu
> To write servers, the best alternative may be to write a C program
> that uses accept(2) and then forks an Icon program once a connection
> is established.
Actually, what I wanted was to manage several sockets simultaneously,
handling connects and disconnects dynamically. I chose to go with a C
process that managed the sockets and wrote to a file which I just poled.
Any better ideas?